'\" te
.\" Copyright (C) 2005, Sun Microsystems, Inc. All Rights Reserved
.\" Copyright 1989 AT&T
.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
.TH NEWKEY 8 "Feb 25, 2017"
.SH NAME
newkey \- create a new Diffie-Hellman key pair in the publickey database
.SH SYNOPSIS
.LP
.nf
\fBnewkey\fR \fB-h\fR \fIhostname\fR [\fB-s\fR nis | files | ldap]
.fi

.LP
.nf
\fBnewkey\fR \fB-u\fR \fIusername\fR [\fB-s\fR nis | files | ldap]
.fi

.SH DESCRIPTION
.LP
\fBnewkey\fR establishes new public keys for users and machines on the network.
These keys are needed when using secure \fBRPC\fR or secure \fBNFS\fR service.
.sp
.LP
\fBnewkey\fR prompts for a password for the given \fIusername\fR or
\fBhostname\fR and then creates a new public/secret Diffie-Hellman 192 bit key
pair for the user or host. The secret key is encrypted with the given password.
The key pair can be stored in the \fB/etc/publickey\fR file or the NIS
\fBpublickey\fR map.
.sp
.LP
\fBnewkey\fR consults the \fBpublickey\fR entry in the name service switch
configuration file (see \fBnsswitch.conf\fR(5)) to determine which naming
service is used to store the secure \fBRPC\fR keys. If the \fBpublickey\fR
entry specifies a unique name service, \fBnewkey\fR will add the key in the
specified name service. However, if there are multiple name services listed,
\fBnewkey\fR cannot decide which source to update and will display an error
message. The user is required to specify the source explicitly with the
\fB-s\fR option.
.sp
.LP
In the case of NIS, \fBnewkey\fR should be run by the superuser on the master
NIS server for that domain.
.sp
.LP
In the case of LDAP, \fBnewkey\fR should be run by the superuser on a machine
that also recognizes the directory manager's bind distinguished name (DN) and
password to perform an LDAP update for the host.
.SH OPTIONS
.ne 2
.na
\fB\fB-h\fR \fIhostname\fR\fR
.ad
.RS 15n
Create a new public/secret key pair for the privileged user at the given
\fBhostname\fR. Prompts for a password for the given \fBhostname\fR.
.RE

.sp
.ne 2
.na
\fB\fB-u\fR \fIusername\fR\fR
.ad
.RS 15n
Create a new public/secret key pair for the given \fIusername\fR. Prompts for a
password for the given \fIusername\fR.
.RE

.sp
.ne 2
.na
\fB\fB-s\fR \fBnis\fR\fR
.ad
.br
.na
\fB\fB-s\fR \fBfiles\fR\fR
.ad
.br
.na
\fB\fB-s\fR \fBldap\fR\fR
.ad
.RS 15n
Update the database in the specified source:
\fBnis\fR (for NIS), \fBfiles\fR, or \fBldap\fR (LDAP). Other sources may be
available in the future.
.RE

.SH SEE ALSO
.LP
.BR chkey (1),
.BR keylogin (1),
.BR nsswitch.conf (5),
.BR publickey (5),
.BR attributes (7)
